I'm very new to Bootstrap and Django and I was wondering if I should stick to Bootstrap 3 or use Bootstrap alpha. What do you think? And the other thing is can I use both 3 and 4 on a same site or there will be issues? Thank you for your opinions.
Well that all depends...
Are you creating a project for someone who's paying you that you need to be sure it works. - Use stable.
Are you simply experimenting and tinkering with code and not afraid to make small/big changes later and know Bootstrap already? Use alpha.
If your completely new to Bootstrap and never touched it before. Use stable.
Alpha may have changes later on. So it would be pointless learning something that isn't set in stone and maybe completely different later.
And the other thing is can I use both 3 and 4 on a same site or there
will be issues?
There will be lots of issues. Besides maintenance headaches, it would defeat the purpose since they would both attempt to overwrite each other, and top it off, your page load times will go up since your attempting to load 2 frameworks. (The less code the better!)
I would also recommend starting to learn software terminology to make better sense of things when you start comparing libraries/frameworks.
i.e.
Alpha = Very uncompleted, will introduce features, or big changes. (Good chance of bugs that have or haven't been noticed yet.)
Beta = Very close to completion, will not introduce features
(usually not anyway).
Hope this helps, and good luck!
Related
I'm planning to write an application for managing a game-server in Red. It should be extendable by using interpreted Red scripts. Now, I want to set restrictions for this scripts (I want to "sandbox" them) and remove specific functionality like I/O, and some other functions.
I know that in Rebol such things are archived using secure, but is something similar possible in Red too? I've already done some experiments with contexts, but I just don't get it.
Thank you.
Red is probably not at the point the will satisfy your needs yet. secure will be added in future versions, but right now you can change everything, if you really want to. Remember, it is still alpha version.
You can take a look at this article that describes some ways to make changing stuff harder (but not impossible) in the meantime.
I'm familiar with developing webapps and website with Bootstrap (v3 and v4), but now I'd like to start using Semantic UI.
After experimenting a bit I feel like Semantic UI offer less composabilities than Bootstrap, but I'm probably missing some things.
For instance, I'm still unclear on how to I mute a text? Bootstrap has a text-muted class, but I can't find equivalent in Semantic UI
Question
Can you describe the paradigm shift that is necessary? Here are a few questions that might help you frame an answer:
What should I stop doing/using;
What should I start doing/using instead?
Are there any server-side considerations/restrictions?
N.B.: I'm not looking for a detailed comparison between Semantic UI and Bootstrap.
Well, I had some Bootstrap and a lots of Foundation background before using Semantic UI, and the transition was easy. Now, when I'm forced to use Bootstrap, everything seems illogical there.
So, working almost 6 months on Semantic UI, I learned some of the things that helped me:
When you get the hang of the semantics, it will be considerably easier. When Bootstrap forces you to use weird illogical abbreviations, then Semantic UI is natural language based. For example "ui inverted huge equal width form" will come out the way it sounds because you understand how things work together.
The docs. I think Semantic UI has superb docs with examples, so if you don't know how to do something, you find it from the docs. I've only encountered couple of things you cannot find from the docs (e.g. Nag).
There are some restrictions. For example, older Android, iOS and IE browsers are not supported because of the Flexbox. And there ARE bugs, so probably you have to fork and/or do pull requests and some Github issues and wait for a long time to have them fixed in main repo. Or rewrite some of the components (we ended up rewriting Sidebar because it didn't perform on mobile devices). But we didn't really see point in supporting legacy stuff that much anyway.
The box model and positioning is different to what you've used to in Bootstrap, but in a way, it's a lot simpler when you get the hang of it.
Don't expect a lots of helper classes, write them your own.
Learn to use LESS, Gulp etc. from day one - it will save you from lots of headache and will increase your productivity. Also extending/overwriting Semantic UI is a good idea, when you want your own design.
All in all, we had issues, but looking back, we actually won in development time, because Semantic UI has most all the tools available you need to develop modern UI.
Changing Career from iPhone application developer to Tester makes me to learn about basic testing.I need to hone my testing skill.what are the ways to improve
I'm testing ~5-10 (small) applications per year so I'm no expert by any means, but this are several things I find quite useful:
Think out of the box. You are familiar with the workflow of the application. You know what your designers thought when implementing
functions. After checking these regular patterns I try to think about
the app completely different and try out new unconventional
workflows.
Try breaking it. Type text where numbers should be, try copying text from the outside into numberfields, tap multiple buttons and
hold them while using one normally. Use your UIElements while turning
the device. Be creative about it - Go apeshit on it! ;-)
"A common mistake people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools." - Douglas Adams
If allowed, hand this application to a 10 year old and see how he
uses it.
Go fast. When jumping between views your eyes will notice small shifted pixels automatically.
When done, check out this awesome tool: UIAutoMonkey (Coming back to that apeshit part ;))
If you are entering in the field of testing, then make sure you follow the below steps/things :
Clear the basic concepts of testing (You can refer the loads of online material for this)
Go for Manual testing first as it will be easy for the first time.
Try to break the things.
Test only when you have clear guidelines. Don't assume anything.
Happy Testing !!
I'm looking for an implementation strategy to ease A-B testing / Beta testing. I don't see any code/plugin available for any framework. If not for a direct solution, let us at least brain-storm the requirements/expectations from the component:
There are already a few threads around my query..
Is there a PHP CMS with builtin A/B Testing Support?
Anyone got any good strategies for A/B testing with the Play Framework?
Beta Testing
As no one's answered this question, I'll attempt to do so.
Basically, I'm not sure if there's a directly useful connection between your PHP framework and your A/B testing needs. I think this is mainly because what you're testing can be almost anything: the colour of a conversion-sensitive button, a page layout, an entire registration funnel, etc. These don't inherently have anything to do with your PHP framework and there are lots of options for how you could do your testing.
Another issue is that you might not really know the parameters of what you're testing until you start testing. Your testing might lead you down a way that you didn't really even consider, so how could you have accounted for it in how you built the site? If you need a REALLY wide window for what you'll be testing, you're probably better off not building it at all and using some type of vapor/smoke-testing to get the basic concepts right first. Not everything can be subjected to testing and you'll still need subjectively-generated hypotheses as your test cases (and your testing will be only as good as your hypotheses).
If you have something very specific that you need to test repeatedly over time and want to build this flexibility into the system, then I'd look for the most obvious solution in the framework to make it happen. For example, if you're using Symfony and if you think that you'll need to test 50 different sidebar variations for a page over the course of 6 months, it probably makes sense to build it as a slot/component so you can build some logic around simplifying your testing and swap those sidebars with ease. I'm not sure why it would need to be anything more complicated than that.
Overall, I'd also add that the role of A/B testing should to guide your product to sell/convert/monetize/engage better. Unless you're building some type of a testing platform, I wouldn't over-think it. I tend to see that most sites fail to test sufficiently not because the system isn't flexible enough for various test cases but because top management won't give enough product/dev time for it, or because people aren't making enough use of their analytics packages to draw even the most basic of conclusions.
Hope that helps.
http://phpabtest.com/ looks like a pretty easy to use framework that comes free!
I'm considering adopting .nettiers for a new project as it seems to provide a lot of functionality I could use.
Is anybody using it in anger (I'm getting the feeling it hasn't got the following it once had) and if so, what are your perceptions of it?
Also, I can't find any comparative performance metrics against things like SubSonic. Anybody have any strong feelings about its performance and scalability?
Many thanks
Tony
When I used NetTiers, I was very happy with it to an extent. You really need to learn the best ways to use it. There were definitely some weird bugs, things that had arbitrary limits and so forth. You have to be careful with it but it can definitely improve your productivity if you learn. I know CodeSmith has started putting more resoucres in it. The version 2.3 might be very solid. Although, the latest current stable version may be pretty solid, I haven't used it in awhile.
Honestly, at this point I prefer LLBLGen. I did try SubSonic a couple times. I didn't run into major bugs but I ended up switching, in both cases, to NetTiers. With SubSonic I felt that I was just typing out way too many string literals and it just didn't feel as mature as other alternatives.
Look at this. It provides you with a good X vs Y comparison between the two of them.
A Key point that i always revise when selecting a framework to work with is:
Will this Simplify, Make me more Productive, if you answer "Yes of course" to this, it doesnt matter what other benchmarks say, even if it's 10% slower in running than SubSonic or even faster, you should go with the framework you develop the fastest and most that you are the most comfy in.
I had some time this afternoon to run a head to head comparison between netTiers and SubSonic.
I used code generated using SubStage (part of the SubSonic 2.1 release) and I used RepositoryRecord as my base class.
I ran the same test against the same database using code generated by .netTiers 2.2
The test was a derivative of the one that Rob Conery used in his post:
http://blog.wekeroad.com/blog/subsonic-scaling/
When i say derivative, I mean I just wrote 100,000 records into the database.
I repeated each test on the same PC three times.
I found that .netTiers accomplished the task in 90 seconds.
Subsonic completed it in 104 seconds.
There was no more than a one second deviation from these averages.
Look at this. It provides you with a
good X vs Y comparison between the two
of them
Thanks - I've already read this post before, but it's over two years old and both projects have advanced a great deal since then.
Asking whether or not a framework will make me more productive or not is a very important consideration, but it's not the only one.
Another for me has to be "am I going to lose potential productivity gains because the framework I adopt is full of bugs, nasty to use, or just a PIA?" which is why I asked if people are using it in anger and what their experience is.
If .nettiers is 10% slower than subsonic, but gives me a whole bunch more features (such as better validation, business rule enforcement etc) then I can live with that. If its ten times slower, then I'd not consider it.
Many thanks
Tony