my EB wishlist

[jordan]

He, never knew there was a dedicated section to EB suggestions ?
My EB wishlist ... .

01. Dataset
add dataset in dataset

02. Option list
add a value and hidden value, so the user can be presented with a cleaner choice input

03. File + Gallery
add to asset manager, so external content is saved relative to the project
+Templates ?

04. A new multi file system property
add a new external content property, so multiple external files can be added in one instance
+add to asset manager, so external content is saved relative to the project
+Templates ?

05. A new title property
add a new title property, so categories can be sub-categorized
so the user can be presented with a cleaner oversight

06. A variable external file name with extension
ie. $myVariable$.xml
so the user only has to enter a name without the extension, or even better ... myXml$myID$.xml

07. Color property
a way to add transparent as option (editable?)

08. Dataset
dataset data be saved with the project,
so extensions with dataset can be updated without having to reload entered dataset in an existing project

09. Dataset
add a copy/paste function for the user to easy/better manage dataset entries

10. Dataset
add ... files can target user specific folder

11. Categories
a new option to start an extension with 'all opened' or 'all closed' or 'specific' category
so the user is not presented with all the categories at once

12. Not directly extension builder (related)
better icon distinction in the WB extension manager between user/official extensions


Of course all of these will be available in the next EB release . .

UPDATE:
green = added in EB3 + EB4 . .

[Pablo]

Thanks for your suggestions list. I will start working on a new version of EB in the next two months.

[jordan]

GREAT news! Thank you very much for your time! . .

[Pablo]

Can you give me more details about items 3, 4, 8 and 10?
Or examples how you would like to use these options?

[jordan]

hello support,

03. Content safety measure
-- GOOD:
Gallery & File content IS saved relative to the project … BUT …
-- BAD 01:
The path in the Gallery remains absolute, if you change the Source structure/name (the Path) the content is lost ?
-- BAD 02:
If you create an extension which uses a Gallery property and a File property at the same time
And the Gallery is placed in position above the File property … then
The File property will not be saved relative to the project, instead it will be replaced by the last entry of the Gallery, after project save ?
-- BAD 03:
If you create an extension which uses a File property and a Dataset File property at the same time
And the File property is placed in position above the Dataset File property … then
The 1st Dataset File entry will be replaced by the File entry, after project save ?

I think I could find some more twists, but there seems something faulty with the manner files are stored/saved

08. Extension update
At the moment Dataset data seems to be saved with a project ?
Cause when new properties are added to a Dataset then that extension will not function any longer in a saved project
Unless the Dataset property are reloaded (Dataset opened/OK/closed)
This does not happen with any other EB property, properties can be added and when opened in a saved project the extension will continue to work ?

10. File structure
Dataset File property behaves the same as the normal File property … add … 'Publish this file to the user defined target folder'

=======

04. Dynamic change of content
This is more a personal feature I love to have …
I have created this extension jor_aniMate, with it you can basically create your own new extension
So one extension creates multiple extensions by combining modules and adding custom script
This can of course only work if you can add external content for the extension that is created
Since it is one extension that creates multiple extensions it is impossible to know what the content is going to be
So … if there would be one property that holds all content then the extension can be created to use that content
Basically the same as a simplified File Publisher, which is what I use at the moment to get my result
But it would be great to have that combined in one extension, so content data is not scattered but contained


any more explanation needed just let me know . .

[Pablo]

Thanks! I see what I can do.

[Pablo]

A beta version of Extension Builder 3.0 is now available:
viewtopic.php?f=48&t=44712

Many of your suggestions have been implemented. Others remain on the list for the future…

[jordan]

Many of your suggestions have been implemented. Others remain on the list for the future…

TNX! . .

[jordan]

hello support,

Thank you for the EB3 release!

01. Minor: the manual is not correct on sorted values ... it should read ...
"If this option is enabled then the values will be displayed in the same order as they appear in the Extension Builder properties overview."

02. Minor: dataset option list
the function works and all . . (thank you) – but could it maybe in a future version display the correct value also in file dataset view ?

Thanks again for all your time and work . .

[jordan]

I found ...

the jQuery settings are not remembered (shown), and are lost when reopened

is it ok if I post any findings here or is it better in a new topic ?

[Pablo]

the jQuery settings are not remembered (shown), and are lost when reopened

Thanks, this is now fixed. Please redownload.

but could it maybe in a future version display the correct value also in file dataset view ?

This is not possible the data view displayed the actual values (the displayed values are not stored inside the dataset).

"If this option is enabled then the values will be displayed in the same order as they appear in the Extension Builder properties overview

This is not correct (according to the documentation of the property grid):
If the option is enabled then property values and/or property categories are sorted alphabetically
If the option is disabled then property values and/or property categories go in the order in which they have been inserted.

[jordan]

01. yep, thanks it works correct now

02. ah ok, well the function works good, that's what matters anyway, would have been a bonus

03. that is how I would expect it to work indeed, but it doesn't, that's why I reported it earlier ?
---- if you disable the 'Sorted Values' it starts to sort the properties
---- if you enable the 'Sorted Values' it shows as if they were inserted

[Pablo]

Unfortunately I cannot change how it works. I've just added these options to give the creator of the extension control over this this standard functionality.
It can be either turned on or off.

[jordan]

hmmm, I don't understand ?

if you disable the 'Sorted Values' then it starts to sort –(this is what occurs)–

so either the function has to be changed or the manual has to be changed
cause the EB3 manual says

if you disable the 'Sorted Values' then the values will be displayed in the same order as they appear

that doesn't happen (the opposite occurs)

[jordan]

hello support,

two things I found ...

01. dataset value/hidden value:
at first dataset enter the real value will be used instead of the hidden value
ie.
small~100
big~200

at first dataset enter the value will become - smallpx
you then first have to select the actual property (click OK), then the value will become - 100px (=correct)


02. dataset value/hidden value:
when BLANK is used it does not hold on to the real value but will show the hidden value (a BLANK space)
ie.
false~
true~whatever

when false is selected it will revert to (the hidden value), it will show a BLANK space ?
this works correct under the normal option list, it will show "false"

[Pablo]

1. I will look into this.

2. You cannot use a 'blank' (white space), it will be stripped bu the XML parsers.
If it's for HTML you can better use ' ' (without the quotes)

[jordan]

01. thank you

02.
but the value is not the problem, the value is correct … it will display a blank space … so it is converted correct
the problem is the real value is switched for the hidden value, the real value is not stored

[Pablo]

the problem is the real value is switched for the hidden value, the real value is not stored

This is because the XML parser will see the space as an empty value and ignore it (as if there was no hidden/real value).

[jordan]

yes, I figured at much …
but can it not be set so that "if it is a blank space" then insert a blank space and keep the real value ?

some sort of workaround for me would be to create an empty variable like …
var myEmpty='';
false~'+myEmpty+'
that would work in some cases …

but can that not be done internal, "if it is a blank space" then insert a blank space and keep the real value ?

[Pablo]

If it's for HTML you can better use ' ' (without the quotes)

[jordan]

most of the time I use dataset it is on Javascript   won't work then

[jordan]

thank you for the EB3.0.1. update support!

[jordan]

hello support,

could the EB3 color input maybe be made editable, so you can input i.e. transparent or a variable instead ?

[Pablo]

That will be difficult because it requires a redesign of the color selector, which is used by almost all WWB objects.

[jordan]

hmmm, I figured as much, just hoped you could wave that magic wand of yours again
will just have to work around it somehow … argh!

ps:
something else, just curiosity, the color picker has 3 modes Html, Flash and other
what is other used for ?

[Pablo]

Color formats:
HTML: #00FF00
Flash: 0x00FF00
Other: 00FF00

[jordan]

yes, but when is 00FF00 (other) ever used ?

[Pablo]

It was requisted by a user in the past, if I remember correctly it was for a flash based extension.

[jordan]

ah, very specific use then … ok, thanks for the info