I'm sure this question has been asked and answered before but I can't find it so I apologize in advance.
Since Dmitry is the author of both and the look very similar, I'm wondering what the major differences are and why I should might choose one over the other. They both look great!
PhotoSwipe : You can swipe through images.
Magnific : You use buttons to go through images.
PhotoSwipe seems to be more up-to-date with current technologies and also the design is better than Magnific.
Personally I would choose PhotoSwipe.
Related
I am wondering if it is possible to make a stuffs in one psd and link it to another psd so that when I change one the other changes also. I know it sounds kind of weird but I am going to need this.
I am designing a website with about 20 templates and every time I change something in the header I need to open all the other psd and apply the changes. And I cannot do all the templates in only one psd for business reasons.
Google did not help me much or maybe am searching with wrong keywords.
Thanks for your help
Sure, go to the File menu and click Place linked... to link a Smart Object.
If you don't have access to the latest Photoshop, which has this feature, I would suggest to overthink your workflow.
Actually I would suggest it anyways, because I think, designing websites using multiple PSDs, possible having 70% or more showing the same, isn't that efficient. So far, I personally was never in need of doing that.
So, if your websites aren't changing drasticly on every page, I don't see any need in multiple PSDs. This way, the urge for your requested feature (that you can't have anyway without a new Photoshop) would probably be lessend.
In the last days I have found the componed based entity system.
I think i understand and know how it works, but if I try to implement it, I get a lot of problems.
Here a diagram with the most Problems:
http://s7.directupload.net/file/d/3327/pzy7kanj_jpg.htm
And I wonder me, can I add the same component twice to an entity, or should I dont allow this?
If no, how I can add multiple sprites to an Entity?
And if a make a CollisionComponent or a Physik Component, the Physik and the MoveComponent must communicate, right ?
I hope anyone can me help.
Here I have made another diagram, from Ideas:
http://s1.directupload.net/images/130725/5p83qysu.jpg
Ok there seem to be a lot of related questions between this post and the diagrams you linked to. The answer to these questions are 'it depends.' and I am guessing you would like some guidance on the subject of CBSEs rather than one line answers to all of your questions. Rather than try and regurgitate the discussion based on similar queries I will post some links here that should get you thinking more about these issues.
First there is the ES wiki. This wiki is still in its infancy, but it holds some great discussion on entity systems.
Next, there some really productive discussion over at gamedev stack exchange (maybe this question should be moved there as well). First take a look at this question, it's a good starting point because it explains why there are no clear trends in ES design (when that answer was written) and from what I've seen it still holds true today. Then there is an absolutely amazing answer given by Byte56 that explains the basics of the system-component approach extremely well, and is well worth reading even if you think you've already got a handle on it. Next there is a helpful series of questions asked by Yannbane. These questions address some of the finer points in more detail. Here are all three questions. Also, there are some questions on how to integrate input and Game States.
Finally, you should check out some open source entity systems that have had a lot of attention such as Artemis written in Java (There seems to be a server issue right now for that link but this article is a good intro, and there are c# and c++ repositories available, so you can dig into some code). There is also ash written in AS3.
Now I feel I must answer one of your questions directly:
And if a make a CollisionComponent or a Physik Component, the Physik and the MoveComponent must communicate, right ?
From the diagrams you linked to you seem to be using the systems-based approach (similar to artemis). From my reading I believe that this is one area that has been generally agreed on by the community: in the system approach the idea is to centralize the component logic so that (aside from a few simple methods as mentioned in the answer to Yannabe's second question) the component is little more than a data container. So if your components are stored in entities then your systems are required to sift through all of your entities. The systems that require more than one component should be asking each entity for all the components it needs to do its work. If it doesn't find all of those components the system should move on. So based on what you have decided so far the answer is no, components should not be communicating with eachother.
Anyway, good luck on this.
I'm currently stack at creating an app.
Our requirement is to make "book viewer" app similar to the iBooks. Each of the book is just series of images (JPEG or PNG) and not a pdf. So it's more like an image viewer in a sense.
The main view is going to be like "horizontal tableview", which the user can scroll horizontally the covers of the books, click it to download and open the book (which led to another page view). The row for the cover should be at least two since there's two "type" is set for the books. This part is more like a "pulse-style" bookshelf with UI similar to this.
When I thought of how to implement this behaviour, I found the way with UITableView just as described here. However, as an objective-c beginner, it's little complicated for me to use this, and our requirement has also each "cell" must have multiple buttons to set each book as "favourite" or "downloaded" etc... and this could be more complicated if I choose to use the UITableView.
So I came to think of using UIScrollView to line up the book covers, embedding each cover as an UIImageView with buttons. But I really don't know if this is the right direction, sicne the UIScrollView has no "reload" function, and the requirement also stated that the user should be able to find the books by using "search bar" at the head of the bookshelf view.
As you can see, I'm completely confused and depressed because I don't know how can I achieve this. I searched around google and several answers here at stackoverflow suggest using AQGridView or EasyTableView. They are both great, but again too complicated to implement these into our requirement...
Which way, or how should I implement this dynamic "pulse-style" bookshelf like feature?
I think my question is a bit vague, but I'm also not clear what to ask here because I really don't know how to do this. The Android version of this app is already achieved this requirement with fairly simple and easy to understand codes (since I have some experience in Java), but for this Objective-C, everything seem needlessly complicated...
Any help would be appreciated.
Thank you.
<preachy>The fact is that you have made a mistake by trying to make this app with a complex interface full of non-standard UI components when you are “an objective-c beginner”. I understand that this may not have been your decision; it may have been forced on you by the guy that signs your paychecks. Nevertheless, it is not reasonable to expect that you can just implement this app before you've spent the time working through tutorials and reading documentation for the programming language and libraries required to build it. We all have to learn the alphabet before we can start writing limericks.</preachy>
That said, if your app can require iOS 6, and you can take the time to learn a bit of Objective-C and iOS programming, it sounds like this would be pretty easy using UICollectionView. Apple did a couple of sessions about this powerful new class at WWDC 2012. I recommend you watch the videos:
Session 205 - Introducing Collection Views
Session 219 - Advanced Collection Views and Building Custom Layouts
You can also easily find some tutorials about UICollectionView using your favorite search engine.
Take a look at Collection View's
You can even download some sample code to see how a grid layout can be accomplished.
I am using the Haxe multi-platform programming tool (http://haxe.org) which, among other things, can generate JavaScript output. I would like to know if anyone has already done a "wrapper" library to interface Haxe with SlickGrid.
Doesn't look like one exists yet... sorry!
Unless someone has made one but just not shared it. Could be worth asking on the haxe mailing list / google group? You'll get a wider audience than on stack overflow.
If it looks like no one has done it, you can write your own... it's probably quite do-able. And not too hard either. I'd be happy to help you figure it out as you go... cause I might want to use it one day too :)
If you do decide to take that route I think the best option is to post on the mailing list, and we can help you out from there. There's also a document on the wiki with some instructions:
http://haxe.org/doc/js/extern_libraries
This stuff is always a bit daunting when you first get started, but don't be afraid to ask for help and hopefully you'll be up and running in no time.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I want to build a simple blog which contains:
A home page with blogs listed in the typical fashion: Title and content, plus read more to open a single entry.
A publish area: Title and Content
admin area to delete and modify posts.
No need for tags, users, or dates.
Take a look at this draft:
I have been looking for tutorials on the internet, but haven't found something simple enought to start working with.
EDIT
Found two nice tutorials. Haven't tested them, but looking at the
comments they seem reliable.
In this tutorial the steps look pretty straightforward and basic.
I'm still a noob in OOP, so this might be right for me:
http://css-tricks.com/1907-php-for-beginners-building-your-first-simple-cms/
This one is more elaborated, it contains users, dates, and tags. I
put it here for future reference:
http://net.tutsplus.com/tutorials/php/how-to-create-an-object-oriented-blog-using-php/
But since you can't use WordPress, what do you need?
You obviously got a pretty concrete idea of how to build it. I think you should refine that further, and start building.
Don't overdo it in the beginning. Start by designing a very simple blog. Each post containing just a title and contents. Skip the use of WYSIWYG editors, and advanced admin options. Just make a view page for a post, a view page for the list (chronological), and an admin page to edit or add posts. Publishing can be done by just adding a simple 'published' field, which you can toggle using a checkbox.
Don't bother with users yet. Just use basic authentication.
If you stick to those simple definitions, you should be able to get a working blog in a short time. After that, you will have some idea of the possibilities (of your possibilities too) and you'll be able to build on the base you got.
If there would be a very extensive tutorial on building a blog, you would eventually still just be copying the samples in that tutorial. It's more fun to think of something yourself and search or ask help for specific problems you run into.
Maybe you will have to start over at some point. Remember, if you build something for the second time, you'll build it faster, and it will be better.
But it won't be good until the third time. ;)
Just do it. If you want to learn anything, simply figure it out. This is straightforward stuff. It'll teach you basic HTTP processing, some simple DB design and integration. Set up PHP/Perl/Python/Java/R/Common Lisp, add in MySQL or SQLite or whatever, follow a couple of HOWTOs, and just do it.
Really, you "don't need us" for this. Just break it down in to pieces. What are the right pieces? Whatever feels right to you. Seriously, unless you plan on hosting it to the wild world with some sensitive information, you really have nothing to lose here by just doing it yourself and pulling it off with amazing perfection or having it come out as a complete disaster. Both are rewarding in its own way.
If you have a specific question about a specific piece, you can come back, or head over to ServerFault, but you will likely be able to pull this off with even a teeny bit of persistence.
So just do it. Grab the keyboard by the plug and work the problem. It's better this way.
Found two nice tutorials. Haven't tested them, but looking at the
comments they seem reliable.
In this tutorial the steps look pretty straightforward and basic.
I'm still a noob in OOP, so this might be right for me:
http://css-tricks.com/1907-php-for-beginners-building-your-first-simple-cms/
This one is more elaborated, it contains users, dates, and tags. I
put it here for future reference:
http://net.tutsplus.com/tutorials/php/how-to-create-an-object-oriented-blog-using-php/
For me this is just great run on tornado and app engine very basic and very good but i don't like comments and fb plugins etc try it source code.
A previous ver without tornado is also available: GitHub