Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

Moderators: martimiz, UncleCheese, Sean, Ed, biapar, Willr, Ingo, swaiba

************* WIN A SILVERSTRIPE BOOK! *****************


Go to End


16 Posts   3498 Views

Avatar
UncleCheese

Forum Moderator, 4102 Posts

30 January 2010 at 7:45am

Edited: 15/03/2010 5:28am

Hey, DOM users!

I have an extra copy of the Silverstripe book (English) that I am giving away to a randomly chosen user who responds to thread.

In 2010, I am planning a major refactoring of the DOM module, and it will be a great opportunity to add some new features. In your response below, please describe some of the features you would like to see in the next generation of this module.

I will choose the winner one week from today. Thanks, everyone!

Avatar
sparkalow

Community Member, 8 Posts

31 January 2010 at 6:48am

Edited: 15/03/2010 5:28am

Thanks for this module.

I would like to see support for farmville - I mean a simple way to use it standalone or as a substitute for model admin. That is not attached to a page.

Avatar
Juanitou

Community Member, 323 Posts

31 January 2010 at 7:26am

Edited: 15/03/2010 5:28am

Hi UncleCheese!

Please don’t hesitate to choose me randomly and don’t forget the dedicace for yours Juanitou… ;-)

Another advantage of your wise choice: I’d ask less beginner questions and contribute more intelligent solutions to the forum.

I’m using DOM at its most basic, I don’t need any more functions and, sincerely, I’d like to be able to contribute more than to wait for the experts to do it in their spare time.

Best regards;
Juan

Avatar
bummzack

Community Member, 904 Posts

1 February 2010 at 9:24pm

Edited: 15/03/2010 5:28am

Hi UncleCheese

I already own a SilverStripe Book, so you can exclude me from the competition.
Anyway... my top 3 wishes for the new DOM Release:
- Keep up the good work and awesome support!
- Add more comments to your code. This has several benefits: Automatic API Docs, Other users can figure out what's going on and eventually subclass the DOM for specialized needs... and all the other obvious advantages
- Bug-Tracking Software to report and track DOM bugs/issues/requests.

Best regards - Roman

Avatar
Fuzz10

Community Member, 791 Posts

2 February 2010 at 3:01am

Edited: 15/03/2010 5:28am

Also already have the book , so you can exclude me too ...

Love the module so far ! Awesome job and thanks again for your hard work.

My ideas:

- Validation for input
- Feedback hooks to the user (for example displaying a message in the case of a cascading delete)
- Improve the re-usability of some parts (for example the modal windows can also be used for "normal" images in the rest of the website , inclusion of parts of a gallery in different pages etc. etc. ). This is , as Banal already states probably more of a documentation issue.

Avatar
UncleCheese

Forum Moderator, 4102 Posts

2 February 2010 at 3:48am

Edited: 15/03/2010 5:28am

Hey, guys, thanks! Here's what I can say so far..

- Validation for input

==> Coming very soon, as part of my jQueryValidator module. Won't be perfect, but will get the job done for the time being. The nice thing about this package is that it's super customizable, so any really specific validation needs will have the option of being handled, where as being locked into Silverstripe's own validation using the Behaviour class, our options are very limited, and customization is a PIA!

- Feedback hooks to the user (for example displaying a message in the case of a cascading delete)

==> Confirmed deletes are almost here. I'm struggling with the best way to implement i18n.

- Improve the re-usability of some parts (for example the modal windows can also be used for "normal" images in the rest of the website , inclusion of parts of a gallery in different pages etc. etc. ). This is , as Banal already states probably more of a documentation issue.

==> Frontend DOM has been on my mind for a long time. I'm not too keen on bundling up a lightbox module, however, because I think that the user should be able to choose and implement a lightbox of his/her choice. A frontend DOM as I see it right now, would be read-only.

- Keep up the good work and awesome support!

==> That's a given!

- Add more comments to your code. This has several benefits: Automatic API Docs, Other users can figure out what's going on and eventually subclass the DOM for specialized needs... and all the other obvious advantages

==> #1 priority right now. DOM suffers from the "broken window" principle -- that is, in neighborhoods where there is one or many broken windows, people tend to just trash the place and treat their environment disrespectfully. Why bother keeping it nice? It's already crappy. Code must adhere to the same logic, and DOM has not been. I created it basically in a weekend, and never estimated how popular it would become, so any bug fixes and add-ons have been fire drill code sprints that are documented poorly, implement hacks, etc. Whenever I think about doing it "the right way", I figure, well, the rest of it sucks, so why bother? So, like I say.. #1 priority in refactoring the code.

- Bug-Tracking Software to report and track DOM bugs/issues/requests.

==> In the works. I'm not nuts about Google code so far, and I'm really daunted by the idea of changing SVN channels, but at the same time, I hate the idea of paying for bug tracking, too.

Avatar
mattclegg

Community Member, 56 Posts

2 February 2010 at 10:48pm

Edited: 15/03/2010 5:28am

Hey UncleCheese,

Looks like can help you there- Id use the book to contribute some documentation reference pages (similar to wordpress codex??) for this plugin and silverstripe in general.

And continue to test/write bug fixes for modules I use.

Happy Coding
Matt

Avatar
Rishi

Community Member, 97 Posts

3 February 2010 at 5:09am

Edited: 15/03/2010 5:28am

hello
first of all like to thank you for your great modules,those has helped me a lot.
regarding the features i would like to see virus checking on upload and validation of input...

Go to Top