Home›Notes›Dolphin 7.0.1 is coming soon

AntonLV

698 days ago in Dolphin Development
Tags: boonex, dolphin, update, test, demo, aqb soft
Reactions: 56 comments •6 points•0 reports
 
 

Dolphin 7.0.1 is coming soon

Boonex is close to releasing a new build of Dolphin 7.0 with a lot of fixes and improvements. Most of the tickets were closed and Boonex decided to install the demo version for test purposes. You may find it using the following link http://www.demozzz.com/dolphin701b Also, you are free to download the development version of Dolphin 7 from the public SVN.

SVN: svn://svn.boonex.com/dolphin/trunk
username: guest
password: guest

But, since it turned out that the download from the SVN is a little bit complicated for regular users, a separate archive was prepared (revision 13794 date 16.03.10) from SVN.

Note.
1. DO NOT INSTALL OR UPGRADE YOUR LIVE SITES WITH THIS VERSION. NO FURTHER IN-BETWEEN UPGRADES OF THIS VERSION WILL BE AVAILABLE.
2. The SVN is updated on a regular basis several times a day. So, if there are errors in your installation you may need to wait and download a newer version a few hours later.

If you found some problems, feel free to discuss them in the Dolphin Betas And RCs forum with the other members. If a number of users have the same issue then you may post a bug report ticket in the Boonex Trac. It should be checked and the problem fixed by Boonex developers shortly. If you post the detailed description of the issue and the way it can be reproduced it will speed up the process.

Thank you in advance.

Plus
Comment•Report
 

Plussed by

 
 
 
 

Comments

Oldest First
|
Threaded
 
 
Please login to post a comment.
deansyme
deansyme•698 days ago
 
any rough timescale for 7.01?
Permalink•Reply•Plus•0 pluses
Nathan Paton
Nathan Paton•698 days ago
 
Judging from posts from BoonExers, and the opened to closed ticket ratio, I want to say somewhere around the end of March. Of course, we never really know what they're planning.
Permalink•Reply•Plus•0 pluses
MichelSwiss
MichelSwiss•698 days ago
 
Some more problems with the Admin Panel using IE7... Members management, Languages settings... Problem with Blogs management still here... Less or no problem with Firefox.
Permalink•Reply•Plus•0 pluses
MichelSwiss
MichelSwiss•698 days ago
 
Some more problems with the Admin Panel using IE7... Members management, Languages settings... Problem with Blogs management still here... Less or no problem with Firefox.
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
- Missing tab on member block on front page (bad css) see pic i uploaded to the site
- Still cannot embed video
- Still using tables - this is 2010 not 2000 - should use div + span
- still using inline style attributes
- W3C validation fails miserably - 161 Errors, 14 warning(s)
- CSS validation just as bad (the custom java hacks do not degrade correctly)
- Also - The vertical scroll bar should be forced on, or the number of menu items in drop down menus reduced as when hovering over them on see more a short page the vertical scroll bar flicks on and off. This is as bad as using; a:hover {font-weight:bold}. It's just one of those things you do not do. Ok, so it's just a template thing, but to be quite honest, it looks like dog doo.

Aditionally (seeing as I'm ranting :) ) - no forums on demo to test + language not compiled. This is a poor show guys - should try to maintain professionalism at all times. Gives me the impression that the final version will be as half cooked as the demo.

/DM

PS - did your project manager review this before release

:)
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
- Missing tab on member block on front page (bad css) see pic i uploaded to the site
- Still cannot embed video
- Still using tables - this is 2010 not 2000 - should use div + span
- still using inline style attributes
- W3C validation fails miserably - 161 Errors, 14 warning(s)
- CSS validation just as bad (the custom java hacks do not degrade correctly)
- Also - The vertical scroll bar should be forced on, or the number of menu items in drop down menus reduced as when hovering over them on see more a short page the vertical scroll bar flicks on and off. This is as bad as using; a:hover {font-weight:bold}. It's just one of those things you do not do. Ok, so it's just a template thing, but to be quite honest, it looks like crap)

Aditionally (seeing as I'm ranting :) ) - no forums on demo to test + language not compiled. This is a poor show guys - should try to maintain professionalism at all times. Gives me the impression that the final version will be as half cooked as the demo.

/DM

PS - did your project manager review this before release?

:)
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
Come to think of it - why is there no default forum??? and why are the language files not automatically compiled??

There ya go - 2 more for the list.

/DM
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
LOL - End of march....

Stroll on...
Permalink•Reply•Plus•0 pluses
deano92964
deano92964•698 days ago
 
I knew someone who insisted tables were a bad thing. That is until they were trying to do something that they just could not get things to line up the way they wanted. I did the same thing in a table in 2 minutes.

CSS can not yet duplicate everything a table can do.

I just don't get this table issue.
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
Div / Span are for markup. Tables are for tabular data. CSS is for layout. Tables are fine when used what they were intended for, otherwise they are just a hack, they should not be used for layout - that's the job of the CSS.

Tables were an early adaptation for controlling layout, as quite simply - they were all there was at the time. People adopted the use of grids to lay out web pages, it was a practice that was widely accepted, and at the time it was a revolution. But times have changed, see more and we now have CSS and web standards.

Now the general acceptance is that content should be contained within markup and css used to render it - that is - tell browsers / printers / phones / screen readers / braille machines / etc how to display it.

Using tables for layout is also bad for content linearisation and consequently also SEO, this is not to mention accessibility. Additionally, the use of tables also seems to encourage the use of inline style.

Admittedly there are quirks for IE that need to be addressed with utilizing Divs instead of tables, but these are all very well documented. There should be no issues getting things to line up in if these quirks are addressed.

In summary - if it looks like it should be in a excel sheet - stick it in a table - if not, don't. And if you want to improve your SEO / content linearisation, then skip tables all together and use Divs.

/DM

Viva le web sémantique
Permalink•Reply•Plus•0 pluses
CodeSatori
CodeSatori•698 days ago
 
Semantics is all fine and dandy, but at the end of the day the question is, how much time and effort are you going to invest into it, and how much time and effort do you expect your users to invest into it. Of course there are redundant uses of tables, but to restrict it to strictly tabular data only is to cater for a heck of a lot of extra work and complications for everyone who tries to modify things from the expert CSS work that works cross-browser in a particular setup.

Tables in select places see more are often the only reasonable way you can go with certain positioning issues if you want to be cross-browser compatible backward to older versions of IE, and not have to do separate style sheets for the said browsers. I'm all for no tables and semantic absolutism, but unfortunately the CSS support in certain browsers with large enough a market share just isn't quite up to notch yet.

If it's simplicity versus semantics, I choose simplicity. When the browsers' market share changes, and when semantics and simplicity go hand in hand, the call is a no-brainer. Until then, it's not as black and white as many would love to have it, and I am personally not interested in having my users to have to deal with hordes well-documented quirks, if there's a clear and straight-forward proven solution that everyone is familiar with, and that doesn't involve battling with quirks.
Permalink•Reply•Plus•0 pluses
kab
kab•698 days ago
 
Why didn't you add Russian titles support in Friendly Links???????????????
Just look - http://demozzz.com/dolphin701b/m/videos/browse/album/-/owner/kabmir
And what is that "dash" do there???
Oh, gushhhhhhhhhhh!!!!!!!
Permalink•Reply•Plus•0 pluses
houstonlively
houstonlively•698 days ago
 
@DeeEmm, RE: - Missing tab on member block on front page (bad css) see pic i uploaded to the site

It's not bad css, it's bad js I reported this problem 2 months ago, and no one is taking it seriously..... even though it affects every single Dolphin 7 site. I fixed this on my own site by modifying the js function that calculates the width of the dbTopMenu. Ther is more info in the ticket and 2 threads that it references.



http://www.boonex.com/trac/dolphin/ticket/1668
Permalink•Reply•Plus•0 pluses
houstonlively
houstonlively•698 days ago
 
Any bugs that Boonex does not feel like fixing, continue to be labeled as enhancements, or they are simply ignored.
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
Regarding web semantics...

I spend a lot of my job working with standards - Australian standards, British standards, European and international standards. They are there for a reason, an important one - commonality.

If everyone follows the standards - in our case browser manufacturers, web coders, designers, wysiwyg editors, software houses, everything is fine, life is easy, things work as they should.

If people do not follow the standards, then we end up with issues like Internet Explorer see more 6 (and 7 and 8), Netscape Navigator, code that does not work, proprietary code, code that cannot be read by site readers, the list goes on. There will not be one web coder here that does not cringe when you say Internet Explorer 6 - it is the biggest headache of the modern web - and all because it does not follow modern standards.

(2000 char limit)
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
If someone comes to your house, and installs a gas appliance - you are happy that they have followed (a mandated) standard - Generally they will need to be licensed to do this - the license demonstrates that they have an understanding of the knowledge and application of the standard.

With a website, there is unfortunately no obligation to do the same, except in one instance - to provide accessibility. Most countries / states have strict laws governing disabled persons - things like wheelchair see more access, disabled toilets, etc. The same actually applies to web sites as well, failure to comply is seen as a form of discrimination. There is actually a precedent in law with Maguire vs. SOCOG where SOCOG was fined $20,000 for non-compliance to accessibility provisions.

Maybe we can get a class action together against Dolphin, I'm sure the fines would be much higher - SOCOG was only one website - Dolphin is used on many many more. In this respect alone Boonex have an obligation to follow web standards - let alone for legal (accessibility) reasons. Ironically SOCOG - the "Sydney Organizing Committee for the Olympic Games." is in the same legal jurisdiction as Boonex - so the precedent directly applies.

So from web coders, I would expect more support for web standards, as, in part, it is a legal obligation. Web standards are not an idealist value, it's something we should all be pushing forwards

/DM
Permalink•Reply•Plus•0 pluses
mtvns
mtvns•698 days ago
 
is there a fix for the chat? I have the problem with logged in users can not use the chat no matter what change I do. Everything runs perfect for admin and guests just not the users that are loged in :(
Permalink•Reply•Plus•0 pluses
DeeEmm
DeeEmm•698 days ago
 
Jeesh - damn 2000 char limit.

HL - I accidentally deleted a nice wordy response to you whilst jumbling everything around to fit :(

Yes you are correct - the width element is actually generated by javascript (god only knows why) - my guess is that the issue it is trying to address is to stop the tab text from wrapping. BUT - this is not the correct way to do this - there are several CSS only solutions to this issue - some of them pretty basic too.

My opinion - it's a typical softie trait see more - over complication for the sake of it - just because you can do something - doesn't mean that you should. Remember K.I.S.S!!!

It's additional baggage like this that causes slow page loads. - why do you need to fix the width property after the page loads?? you know what it should be BEFORE you send the page to the browser - set it at this point if you need to set it at all. In fact in this case you do not even need to dynamically assign a width at all - the element can be made to expand to accommodate whatever text, and not wrap using CSS alone.

C'mon guys.

HL - you are also right that it applies to most of the site - every block with a tab in fact.

/DM
Permalink•Reply•Plus•0 pluses
CodeSatori
CodeSatori•698 days ago
 
DeeEmm; agreed, everything should be up to the standard, which wasn't created to be optional, and is there for very solid reasons.

To pick up from your example of the gas appliance, and to tie it up with what I'm on about, imagine this scenario:

50% of houses on the current market have not been built to work properly with standard gas appliances. You are a gas appliance manufacturer, and have loads of retailers and workshops who buy the goods from you and take care of installing the said appliances. see more Can you, as the appliance manufacturer, just make your appliances to the standard only, and then quote the standard and tell the retailers and workshops to tweak it up from there onward? That would obviously pose a major problem, and cause countless headaches for everyone. People less aware of the standards would blame you for producing faulty appliances that don't work in your house, and retailers would blame you for not providing an appliance that's easy to fit in. With all your love for the standards and understanding of their importance, you would be quite inclined to provide solutions that stray from the ideal as little as possible, while working without a hitch across the current houses on the market.

My attempt towards a solution is launching a massive multi-level campaign to bring down the amount of "bad houses" (bad browsers), starting up in the course of April / May at -> http://stopie7.com -- just a splash page at the moment. Anyone interested in participating in the effort is welcome to contact me for more information. I intend to see through a global rally of web developers united in furthering an environment where web technologies can be deployed the way they were intended, without having to put up with all this crap (thanks Microsoft). Rally on far and wide and loud as long as IE6 and IE7 are marginalized, both mass media and grassroots level.

2000 characters....
Permalink•Reply•Plus•0 pluses
houstonlively
houstonlively•698 days ago
 
ANTON: Here's what you said about the disappearing dbTopMenu items in a PM dated 28.12.2009

Hello

Looks like FF displays the content differently when zoom is used.
OK. We will investigate the issue and fix it.

---
Best Regards
Anton Lesnikov
AQB Soft
Permalink•Reply•Plus•0 pluses
Show more comments »
 
 
 

Site Search

Market

Notes

Websites

 

About BoonEx•Contacts•© BoonEx (ACN 127966581)

PET:0.061085939407349