Recent

Author Topic: Uploading all project code for wiki samples in .zip format  (Read 4463 times)

wp

  • Hero Member
  • *****
  • Posts: 9589
Re: Uploading all project code for wiki samples in .zip format
« Reply #15 on: February 03, 2022, 12:35:43 pm »
I do also not see any reason not to allow .zip file attachments in the wiki
This will not work. Guess how often I wrote here in the forum that users should only include .pas, .lfm, .lpr and .lpi files in a zip and finally found all ppu's, the res, the ico and the exe in the upload.
Mainly Lazarus trunk / fpc 3.2.0 / all 32-bit on Win-10, but many more...

Nimral

  • Full Member
  • ***
  • Posts: 241
  • Keep it simple.
Re: Uploading all project code for wiki samples in .zip format
« Reply #16 on: February 03, 2022, 12:35:57 pm »
I am fairly reluctantly saying that, but since Nadella took over the CIO from Bannon, it does *seem* like M$ has indeed changed course in a way so they let other systems, at least as long as they do not pose a substantial threat to theirs, live relatively unmolested.

I admit, mistrusting M$ has a long history in my mindset, but it is 8 years now that Nadella changed the company policy substantially, maybe it is time to attribute them some trustworthiness.

Anyway, as long as I can get back my sources and metadata and go somewehere else there is a plan B, in case they decide to reverse course. I can always host them on my own webserver, as long as someone is willing to publish the link in the wiki.

Armin.

Lazarus 2.2.0 on Windows 7,10,11, Raspberry Pi OS "Buster", macOS Catalina, macOS BigSur, VMWare Workstation 15

Nimral

  • Full Member
  • ***
  • Posts: 241
  • Keep it simple.
Re: Uploading all project code for wiki samples in .zip format
« Reply #17 on: February 03, 2022, 12:42:41 pm »
This will not work. Guess how often I wrote here in the forum that users should only include .pas, .lfm, .lpr and .lpi files in a zip and finally found all ppu's, the res, the ico and the exe in the upload.

Putting a very tight size restriction on .zip would almost always help. Like always, there may be exceptions, but IMHO they were sparse and not beeing able to handle them would be acceptable.

But nevertheless, I think Davos approach is better, I also like the metadata file idea, am eager to try with the demos I have pulled together during the last half year, when I was, having had some experience with Turbo Pascal, struggling to catch up with modern Object Pascal, FPC and Lazarus. Basically I had to re-learn most from scratch, and I guess it was, amongst others, me who complained that the Wikis don't help much the way they are.
« Last Edit: February 03, 2022, 12:45:25 pm by Nimral »
Lazarus 2.2.0 on Windows 7,10,11, Raspberry Pi OS "Buster", macOS Catalina, macOS BigSur, VMWare Workstation 15

dbannon

  • Hero Member
  • *****
  • Posts: 2022
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Uploading all project code for wiki samples in .zip format
« Reply #18 on: February 03, 2022, 12:54:32 pm »
I do also not see any reason not to allow .zip file attachments in the wiki
This will not work. Guess how often I wrote here in the forum that users should only include .pas, .lfm, .lpr and .lpi files in a zip and finally found all ppu's, the res, the ico and the exe in the upload.

Yes, seen lots of cases like that.  And, perhaps, the second problem with posting on the forum is that its time sensitive, a thread is popular, active discussion, someone posts a tar ball with the answer and then the thread becomes history but that tarball takes up space forever. While no more space hungry than a screenshot, the tarball is more likely to get external links pointing to it.....

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

Nimral

  • Full Member
  • ***
  • Posts: 241
  • Keep it simple.
Re: Uploading all project code for wiki samples in .zip format
« Reply #19 on: February 03, 2022, 02:02:15 pm »
Yes, seen lots of cases like that.  And, perhaps, the second problem with posting on the forum is that its time sensitive, a thread is popular, active discussion, someone posts a tar ball with the answer and then the thread becomes history but that tarball takes up space forever. While no more space hungry than a screenshot, the tarball is more likely to get external links pointing to it.....

I didn't see any reason why to not accept (small) zips in the wiki, not the forum!

But anyway ... I prefer the GIT approach.

I wonder if it is, btw, possible to put a link in a page which does automatically point to GITs "download zip file" functionality? I don't see any good in dropping someone wanting the sources off in the GIT GUI where he has to mess with all the nicely coloured gizmos a while until he eventually finds the zip download menu.

Armin.
« Last Edit: February 03, 2022, 02:15:38 pm by Nimral »
Lazarus 2.2.0 on Windows 7,10,11, Raspberry Pi OS "Buster", macOS Catalina, macOS BigSur, VMWare Workstation 15

dsiders

  • Hero Member
  • *****
  • Posts: 634
Re: Uploading all project code for wiki samples in .zip format
« Reply #20 on: February 03, 2022, 04:02:16 pm »
Yes, seen lots of cases like that.  And, perhaps, the second problem with posting on the forum is that its time sensitive, a thread is popular, active discussion, someone posts a tar ball with the answer and then the thread becomes history but that tarball takes up space forever. While no more space hungry than a screenshot, the tarball is more likely to get external links pointing to it.....

I didn't see any reason why to not accept (small) zips in the wiki, not the forum!

But anyway ... I prefer the GIT approach.

I wonder if it is, btw, possible to put a link in a page which does automatically point to GITs "download zip file" functionality? I don't see any good in dropping someone wanting the sources off in the GIT GUI where he has to mess with all the nicely coloured gizmos a while until he eventually finds the zip download menu.

Armin.

Did you look at the URL on the gitlab web page? It uses a predictable scheme. The address book example would be:

https://gitlab.com/freepascal.org/lazarus/lazarus/-/archive/main/lazarus-main.zip?path=examples/address_book

Lazarus 2.0.12, 2.2.0, 2.2.2, 2.3.0 (Git) / FPC 3.2.0, 3.2.2, 3.3.1 / x86 64-bit / Windows 8.1
Preview Lazarus 2.3.0 documentation at: https://dsiders.gitlab.io/lazdocsnext

dbannon

  • Hero Member
  • *****
  • Posts: 2022
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Uploading all project code for wiki samples in .zip format
« Reply #21 on: February 04, 2022, 12:16:48 am »

.....

Did you look at the URL on the gitlab web page? It uses a predictable scheme. The address book example would be:

https://gitlab.com/freepascal.org/lazarus/lazarus/-/archive/main/lazarus-main.zip?path=examples/address_book

Yes, its deterministic now but I hope, at some stage, the git repo will move under FPC/Lazarus and the actual GUI will be part of the Lazarus IDE. When and if that happens, by far the easiest way for an end user to download an example source will be from the (new) Examples Window built into the IDE. But, if that happens, will not be immediately !

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

 

TinyPortal © 2005-2018