PB 6.0 - ideas

Got an idea for enhancing PureBasic? New command(s) you'd like to see?
User avatar
Mijikai
Addict
Addict
Posts: 1360
Joined: Sun Sep 11, 2016 2:17 pm

Re: PB 6.0 - ideas

Post by Mijikai »

It would be nice to have a custom parameter for every callback (ex. BindEvent()...)!
User avatar
falsam
Enthusiast
Enthusiast
Posts: 630
Joined: Wed Sep 21, 2011 9:11 am
Location: France
Contact:

Re: PB 6.0 - ideas

Post by falsam »

akee wrote:Have a librarian that can compile PureBasic code... Tailbite has served us well...
+1

➽ Windows 11 64-bit - PB 6.0 x64 - AMD Ryzen 7 - NVIDIA GeForce GTX 1650 Ti

Sorry for my bad english and the Dunning–Kruger effect.
User avatar
gally
User
User
Posts: 37
Joined: Thu May 28, 2009 9:07 pm
Location: France
Contact:

Re: PB 6.0 - ideas

Post by gally »

falsam wrote:
akee wrote:Have a librarian that can compile PureBasic code... Tailbite has served us well...
+1
+1
Dude
Addict
Addict
Posts: 1907
Joined: Mon Feb 16, 2015 2:49 pm

Re: PB 6.0 - ideas

Post by Dude »

akee wrote:Tailbite has served us well
I never used Tailbite so I don't know the answer to this: why doesn't TB work anymore? I thought it was just PureBasic code like COMate?
akee
Enthusiast
Enthusiast
Posts: 475
Joined: Wed Aug 18, 2004 9:52 am
Location: Penang, Malaysia

Re: PB 6.0 - ideas

Post by akee »

Dude wrote: I never used Tailbite so I don't know the answer to this: why doesn't TB work anymore? I thought it was just PureBasic code like COMate?
Tailbite allowed us to create libraries so you don't have to code functions that you have already troubleshoot. You can use it like any function in PB with a proper .res file in Residents. However some issues with the strings.

For developers who have created routines prior to developing projects for others where you need to surrender source code, this can help you isolate what you created and want private AND what you want to share.
User avatar
Fig
Enthusiast
Enthusiast
Posts: 351
Joined: Thu Apr 30, 2009 5:23 pm
Location: Côtes d'Azur, France

Re: PB 6.0 - ideas

Post by Fig »

akee wrote:Have a librarian that can compile PureBasic code... Tailbite has served us well...
+1

...And Tree/Queue/Deck
...And bug free 2DSprites lib. http://www.purebasic.fr/english/viewtop ... =4&t=65561
... And native FastStrings type.
...And number specific HashTables (Map with numbers as key)
There are 2 methods to program bugless.
But only the third works fine.

Win10, Pb x64 5.71 LTS
akee
Enthusiast
Enthusiast
Posts: 475
Joined: Wed Aug 18, 2004 9:52 am
Location: Penang, Malaysia

Re: PB 6.0 - ideas

Post by akee »

Mijikai wrote:It would be nice to have a custom parameter for every callback (ex. BindEvent()...)!
Ya! ParamCount(), ParamValue(n)...
User avatar
Kuron
Addict
Addict
Posts: 1626
Joined: Sat Oct 17, 2009 10:51 pm
Location: Pacific Northwest

Re: PB 6.0 - ideas

Post by Kuron »

akee wrote:Have a librarian that can compile PureBasic code... Tailbite has served us well...
I consider this a must-have feature.
Best wishes to the PB community. Thank you for the memories. ♥️
Opcode
Enthusiast
Enthusiast
Posts: 137
Joined: Thu Jul 18, 2013 4:58 am

Re: PB 6.0 - ideas

Post by Opcode »

the.weavster wrote:I remember Fred said in this interview the PB team had been experimenting with LLVM so I'm hoping the killer feature for PB 6.0 will be support for ARM processors.

Edit:
I'd happily pay another license fee for that :wink:
This x100. It would make PureBasic that much more appealing with it spitting out highly optimized code and possibly supporting ARM.
Ulix
User
User
Posts: 48
Joined: Wed Jan 23, 2008 12:45 pm
Location: France, Montpellier

Re: PB 6.0 - ideas

Post by Ulix »


... PB 6.0 will be support for ARM processors.
+1, +1, +1.... for RASPBERRY
User avatar
USCode
Addict
Addict
Posts: 912
Joined: Wed Mar 24, 2004 11:04 pm
Location: Seattle, USA

Re: PB 6.0 - ideas

Post by USCode »

SSL/TLS support for PB's Network library.
swhite
Enthusiast
Enthusiast
Posts: 726
Joined: Thu May 21, 2009 6:56 pm

Re: PB 6.0 - ideas

Post by swhite »

1) I would vote for SSL/TLS support in network library especially so I could create network servers that supported SSL. I have a lot of demand for SSL since I work with payment gateways. This has got to be my biggest need above all others.

2) Arm support would be very helpful as I also do a lot of work in the embedded world and Tibbo is coming out with a Linux based system for ARM processors and it would be very nice to use PB in that environment.

Simon
Simon White
dCipher Computing
User avatar
langinagel
Enthusiast
Enthusiast
Posts: 131
Joined: Fri Jan 28, 2005 11:53 pm
Location: Germany
Contact:

Re: PB 6.0 - ideas

Post by langinagel »

Well...have I ever asked for ARM support ...especially for Linux on Raspberry and such ?

Looks like I'm getting old on this.
https://www.doerpsoft.org

Boost. Work. Efficiency.
User avatar
Tristano
Enthusiast
Enthusiast
Posts: 190
Joined: Thu Nov 26, 2015 6:52 pm
Location: Italy
Contact:

Re: PB 6.0 - ideas

Post by Tristano »

If I were to place a PB 6.x wish on top of the wishlist that would be to make PureBasic more version-control friendly.

In the last year I've seen many new PB project spawn on platforms like GitHub, which makes sense because code collaboration is a great motivating factor in any language trend growth, as well as a personal motivation to invest energy in projects (together is faster, nicer, and better).

Whoever has tried to work with Git and PB projects will surely have stumbled over many issues:
  • PB source files with settings at the end of the source file create problems for different contributors, and quite often even if you disable that option in your IDE some other contributor might forget it on and cause Git to see files changes which are spurious.
  • PB Proejct files contain personal data, which one shouldn't really share over the net
  • PB Proejct files change at each end-of-session because they also store history and checksum data — this also causes Git to detect changes which shouldn't be really commit, and most of all every contributor will be changing the project file, so Git will always mark the file as changed, which is a great hassle that prevents switching branches without Git complaining.
  • Other issues might come up when different contributors use PB on different OSs.
So I really hope that the next Major release of PureBasic will take into consideration the wider picture and general trend of the developers community; and lift all the current settings that make working with VCS tools harder. Hopefully, the current PB project files will change, and allow to choose if the file should contain personal data and project history or not, or maybe the IDE could handle two separate project files: one without personal info, in the project folder, and another one with more details in some temporary folder elsewhere --- the former being a more "universal" project file that can be shared with anyone, works with PB on any OS, and doesn't change unless substantial settings are altered.

Also, I'd like to see project files use JSON instead of XML, or even better: YAML — human friendly please!

(It was really cool when PB introduced the JSON lib, so I might also add the wish that PB 6 will bring a YAML lib too!)

Beside that, I'd love to see an updated SDK, with neat documentation (current docs still mention Amiga!) and with a permissive license --- right now, the license terms of the C include files are that by using them you are granting Fantaise Software all rights to use your code:

Code: Select all

/* === Copyright Notice ===
 *
 *
 *                  PureBasic source code file
 *
 *
 * This file is part of the PureBasic Software package. It may not
 * be distributed or published in source code or binary form without
 * the expressed permission by Fantaisie Software.
 *
 * By contributing modifications or additions to this file, you grant
 * Fantaisie Software the rights to use, modify and distribute your
 * work in the PureBasic package.
 *
 *
 * Copyright (C) 2000-2010 Fantaisie Software - all rights reserved
 *
 */
If there is one thing that makes a language powerful that is the wealth of libraries it offers — especially open source libraries.

The license terms of the SDK include files don't even allow you to publish on GitHub a PB library you create, because they'd conflict with the legal terms of most open source hosting services. There are lots of PB users who just love to share their code freely, but these include files can't be added to the project. Why?

If these SDK files would have been GPL licensed, at least one could publish them with his GPL project.

Really, why? Why make it hard for those who wish to make open source contributions?
You'll find lot's of open source PB code, but very few purelibs written in C.

Collaborative tools make developement happen faster (and better). We've all seen the success of GitHub and similar services.

If the SDK was better documented, more up to date, and with permissive license, probably people would be more motivate to contribute lots of useful libraries.

Should we ask for specific features to be implemented, or should we ask for more freedom in the direction of collaborative open source?
The former is the hands of few developers, the latter goes in a direction were potential contributors are unlimited.

For all the love I have for PureBasic, I often feel that issues like those mentioned above are obstacles that prevent it from unleashing most of its power.
The PureBASIC Archives: FOSS Resources:
User avatar
skywalk
Addict
Addict
Posts: 3972
Joined: Wed Dec 23, 2009 10:14 pm
Location: Boston, MA

Re: PB 6.0 - ideas

Post by skywalk »

IDE:
1. Allow block comments.
;/* Copying from C
blah
;*/ End of block

2. Enable jump to definition of item under cursor.
Procedure.i DoIt() ;<-- This is in another file.
;
;
DoIt() <-- Trigger jump to definition opens file and location of Procedure.i DoIt() line.
Same for variables, constants, DataSection labels, etc.
The nice thing about standards is there are so many to choose from. ~ Andrew Tanenbaum
Post Reply